One-Sentence Summary. Open images and any other files from the WSL2 terminal directly in their native Windows applications.

Abstract. Working in WSL2 often breaks simple workflows like opening images or PDFs from the terminal. This article presents a minimal, reliable shell function that opens any file from WSL2 using Windows Explorer, avoiding common issues with UNC paths and unreliable direct application launches.

Keywords. WSL2, Windows Subsystem for Linux, zsh, bash, Windows, productivity, developer tools

WSL2 is fantastic.

But the moment you try to open an image from the terminal, everything falls apart.

You try:

explorer.exe image.png

Nothing happens. Or Explorer opens the wrong folder. Or Windows throws a cryptic UNC-path error.

Let’s fix this properly — with one small, reliable function.

1 TL;DR

To open any file from WSL2 in its Windows environment, add one small shell function to your config file.

⚠️ Limitation: this works on real paths only (no symbolic links).

2 Quick Setup (60 seconds)

1. Open your shell config file:

   • ZSH ~/.zshrc
   • Bash ~/.bashrc

2. Paste this function:

winopen() {
  explorer.exe "$(wslpath -w "$(realpath "$1")")"
}

3. Reload your shell:

source ~/.zshrc   # or: source ~/.bashrc

4. Open any file:

winopen image.png

Done.

3 ZSH (manual)

Edit your config file:

vim ~/.zshrc

Add this one-liner anywhere:

winopen() {
  explorer.exe "$(wslpath -w "$(realpath "$1")")"
}

4 Bash

The same function works in Bash.

Add it to ~/.bashrc:

winopen() {
  explorer.exe "$(wslpath -w "$(realpath "$1")")"
}

5 macOS, Linux, BSD (for reference)

On Unix-like systems with a GUI, the equivalent is trivial:

open file.png        # macOS
xdg-open file.png    # Linux desktop

WSL2 is special because it crosses OS boundaries.

6 Use It

Reload your shell:

source ~/.zshrc   # or source ~/.bashrc

Then:

winopen image.png
winopen file.pdf
winopen video.mp4

Windows Explorer opens at the correct location.

Select the file. Hit Enter.

The file opens using the default Windows application.

7 The Problem (What’s Actually Going On)

WSL2 runs Linux in a VM. That means:

• Your files live in a Linux filesystem
• Windows apps expect Windows paths
• Windows sees WSL files as UNC paths like \\wsl.localhost\Ubuntu-22.04\home\username\...
• Many Windows applications handle UNC paths inconsistently

So even when a command looks correct, it often fails silently.

This is not user error. It’s impedance mismatch.

8 Why Explorer Is the Right Tool

Windows Explorer:

• Fully supports UNC paths
• Is designed to browse network locations
• Reliably dispatches files via default associations
• Does not suffer from viewer-specific UNC bugs

Explorer is the stable bridge between WSL and Windows.

9 The Correct Mental Model

WSL–Windows integration has multiple layers:

Once you use the right layer, the problem disappears.

10 Recommendation

• Use Explorer for anything under /home/...
• Let Explorer handle UNC paths
• Hit Enter to open files
• Store files on /mnt/c only if you need guaranteed direct app launches

Simple. Honest. Reliable.

11 Final Thoughts

This function is tiny.

But it removes a constant friction point when working in WSL2: previewing images, checking PDFs, opening generated files.

One command. Any file. Native Windows apps.

Honestly, this one made me smile when it finally clicked — fewer hacks, less friction, and a smoother dev loop always feels good 😊

✅ 100% vibe-code certified 💯

DOI: